Pls. include the release to the release_archive.yml as well. For example, check fb6c82d.

@ferenc-csaky Will do - I will add this to the PR when we release so I can put in the correct release date.

Pls. include the release to the release_archive.yml as well. For example, check fb6c82d.

@ferenc-csaky Will do - I will add this to the PR when we release so I can put in the correct release date.

Usually we changed the two files together

Pls. include the release to the release_archive.yml as well. For example, check fb6c82d.

@ferenc-csaky Will do - I will add this to the PR when we release so I can put in the correct release date.

Usually we changed the two files together

I was holding off adding this file to this PR until we have the release date which we need for the archive file. So both files will go together in this PR. Are ok with this approach otherwise I may put in a potentially inaccurate release date that would need amending.
The Kafka 5 change is

• name: "Flink Kafka Connector"
  connector: "kafka"
  version: 5.0.0
  release_date: 2026-06-02
  filename: "kafka"

So I need an accurate release_date I think.

Have I misunderstood anything?

No, you're right.

The web PR merge action belongs to "Promote the release" and should happen after finalizing the release[1]. That means you should have finished released these artifacts when you plan to finally update and merge this PR.

[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235835365#Creatingaflinkconnectorrelease-Mergewebsitepullrequest